Blockchain Digital Cryptocurrency Loan System

ABSTRACT

A cryptographic blockchain computer network digital cryptocurrency loan system that rewards both the loan holder and the loan paying network users with system utility fund tokens for each loan payment made. System utility fund tokens entitle the system users to receive dividend distributions of passive income from a system digital cryptocurrency investment fund.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/415,607, filed Apr. 16, 2020, which is the United States nationalphase of International Application No. PCT/US2020/028594, filed Apr. 16,2020, the disclosures of which are hereby incorporated by reference intheir entirety.

TECHNICAL FIELD

The present invention is in the field of data processing systems fordigital cryptocurrency loan creation and payment. More specifically dataprocessing in relation to systems involving a loan creation and paymentprotocol on a delegated proof of stake peer-to-peer blockchain computernetwork.

DISCLOSURE OF THE INVENTION

As used herein the term currency refers to a transferable object thatmay be accepted as payment for goods and services and repayment of debtsbetween parties. Most currency objects today are fiat currencies. Acurrency object may be a tangible physical object or may be anintangible object existing as stored information.

A fiat currency object, like a paper currency bill, is without usefulvalue itself as a commodity. The fiat currency object derives its valueby being declared by the governing authority of a jurisdiction to belegal tender in that jurisdiction; that is, the fiat currency objectmust be accepted as a form of payment within the jurisdiction of thegoverning authority. Accordingly, merchants in the governing authority'sjurisdiction readily accept payment for their goods and services withfiat currency objects because they know that they can in turn pay forgoods and services in that jurisdiction with such fiat currency objects.However, the modern fiat currency objects of today are not the only typeof currency objects.

Historically, the first type of currency objects developed werecommodity items. A commodity item currency object consists of a physicalcommodity item that has an intrinsic value in itself. A common type ofcommodity item used historically as a currency object was preciousmetals, typically gold or silver. A governing authority would often makemetal currency coins by placing a mark on the metal that served as aguarantee of the weight and purity of the metal. With a commodity itemcurrency object, the commodity item object will retain its intrinsicvalue as a commodity item even if it is not used as a medium of exchangeto pay for goods or services. Thus, for example, a commodity currencyobject that is a gold coin will still retain the value of the gold evenif it is melted down and no longer a coin.

Evolving from the use of commodity object currencies were representativecurrency objects. Merchants or banks would issue written receipts totheir depositors which were exchangeable for physical commodity itemsdeposited with them (e.g. gold or silver coins). Such paper receiptsbecame accepted as a means of payment by merchants. Merchants couldexchange the receipt they had received in payment for the commodityitems deposited with the issuing merchant or bank. Such privately issuedwritten receipts used as a medium of exchange came to be a currencyobject known as a representative currency object. Representativecurrency objects helped commercial parties to a transaction avoid theinconvenience and expense of having to store, secure, transport andexchange typically heavier and bulkier physical commodity currencyobjects when conducting their transactions.

The written receipts issued by private banks exchangeable for commodityitems deposited in the bank evolved into what came to be known as thebanknote. A written banknote is a type of negotiable promissory note,made by a bank, that any bearer of the banknote can exchange on demandfor the physical commodity items on deposit with the issuing bank.Banknotes were originally issued by private commercial banks, who werelegally required by the governing authority of the jurisdiction thatthey operated in to exchange the banknotes for the legal tender of thegoverning authority (usually gold or silver coins minted by thegoverning authority) whenever the banknote was presented to the chiefcashier of the issuing bank. The commercial banknotes traded at facevalue in the markets served by the issuing bank. The commercial banksissuing banknotes thus had to ensure that they could always paycustomers in legal tender (e.g. the precious metal coins minted by thegoverning authority) when a person presented commercial banknotes forpayment.

Eventually, national banknotes issued by the central banks of thegoverning authority for a jurisdiction came to mostly replace theprivate commercial banknotes. In contrast to a private commercial bank,a governing authority central bank possesses a monopoly on increasingthe monetary base in the governing authority's jurisdiction, and alsomints the currency objects which serve as legal tender in the governingauthority's jurisdiction.

Historically, many governing authority central banks also followed thepractice of basing their central bank banknotes with a commodity item,most often gold or silver. Thus, a money system that was a “goldstandard” was one in which the governing authority issued currencyobjects (e.g. paper bills) that could be exchanged on demand into afixed amount of gold from the governing authority. Today for a varietyof economic reasons most governing authorities (i.e. governments) haveabandoned commodity-based standards like the gold standard for theircurrencies: Most government issued currency objects have no basing incommodities and are simply fiat currencies.

While legal tender fiat currency embodiments issued by the central banksof governments have come to dominate the modern economy they are not theonly currencies. Commercially issued currency objects can still existwhere not prohibited by the law of a governing authority. One example inparticular is the development and use of digital cryptocurrency objectsin recent decades.

A digital cryptocurrency is a form of currency that is embodied only inan intangible digital or electronic form, and not in a tangible physicalform. It is also called digital money, electronic money, electroniccurrency, or cyber cash.

Digital cryptocurrency objects are intangible and can only be owned andtransacted in by using computers or digital wallets which are connectedto the Internet or the designated networks. In contrast, the physicalembodiment currency objects, like bank notes and minted coins, aretangible and transactions are possible only by holders who have physicalpossession of such currency objects.

Like any standard fiat currency, digital cryptocurrency objects can beused to purchase goods as well as to pay for services from those willingto accept such digital cryptocurrency objects as payment. Digitalcryptocurrency objects allow for instantaneous transactions that can beseamlessly executed for making payments across borders when connected tosupported devices and networks. For instance, it is possible for anAmerican to make payments in a digital cryptocurrency embodiment to adistant counterparty residing in Switzerland, provided that they bothare connected to the same network required for transacting in thedigital cryptocurrency object.

Digital cryptocurrency objects offer numerous advantages. As payments indigital cryptocurrency objects are made directly between the transactingparties without the need of any intermediaries, the transactions areusually instantaneous and zero- to low-cost. This fares better comparedto traditional payment methods that involve banks or clearing houses.Digital cryptocurrency object based electronic transactions also bringin the necessary record keeping and transparency in dealings.

A cryptocurrency object is a type of digital cryptocurrency object whichuses cryptography to secure and verify transactions and to manage andcontrol the creation of new currency units. Bitcoin, Ethereum and EOSare some of the most popular cryptocurrency objects.

The present invention is a digital cryptocurrency (hereinafter “DC”)loan creation and payment system for use on a peer-to-peer (hereinafter“P2P”) blockchain computer. In a preferred embodiment the system of thepresent invention is deployed onto the EOSIO P2P network delegated proofof stake (hereinafter “DPoS”) public blockchain network that wasestablished by the company Block.one and which is generally known as theEOS Mainnet (hereinafter “EOS Mainnet”). The DC of the EOS Mainnet isthe EOS.

Every user of the EOS Mainnet must have a user digital wallet softwareapplication (hereinafter “DW_(USER)”) that stores data which includesunique public and private cryptographic keys of the user. It is throughDW_(USER) that a user interfaces with and conducts transactions on theEOS Mainnet, and can check the user balances of EOS and othercryptographic tokens (e.g. utility tokens of network applications) thatare recorded on the EOS Mainnet blockchain.

Preferably DW_(USER) is a WEB3 digital wallet. A WEB3 digital wallet isa self-custody digital wallet (i.e. one that is in the possession of thewallet owner, as opposed to the wallet being stored elsewhere on athird-party server) which stores the user cryptographic keys and alsohas a browser which can interface with the third generation of the WorldWide Web (i.e. “WEB3”), including for the usage of a decentralizedapplications (hereinafter “dApp”) running on a P2P blockchain networksuch as the EOS Mainnet.

The EOS Mainnet is a DPoS blockchain network where the block producingnodes are selected by a voting process of EOS Mainnet users who have“staked” EOS with the EOS Mainnet. Staked EOS (hereinafter “EOS_(ST)”)is EOS that is immoveable (i.e. “parked”) on the EOS Mainnet and whichcan't be used by a user for conducting transactions on the EOS Mainnet,such as making payments. The EOS staked by a DW_(USER) (hereinafter“EOS_(ST-USER)”) will still belong to DW_(USER). After a certainmaturity period of time EOS_(ST-USER) can be “unstaked” by DW_(USER) sothat it can again be used by DW_(USER) for conducting networktransactions, such as making payments. For as long as a DW_(USER) hasEOS_(ST-USER) it entitles the DW_(USER) to vote by nominating up tothirty EOS Mainnet block producer candidates. Each nominated blockproducer candidate will receive the EOS_(ST-USER) of DW_(USER) as votes.DW_(USER) can also set up another network user as a proxy to exercisethe votes.

On the EOS Mainnet for any transaction submitted by a DW_(USER) to beprocessed and added to the EOS Mainnet blockchain the DW_(USER) musthave a sufficient quantity of EOS_(ST-USER) to access the EOS Mainnetnetwork resources (e.g. the RAM, CPU and NET resources of the networknodes) which are required to process the transaction. A DW_(USER) on theEOS Mainnet is entitled to an exclusive percentage of EOS Mainnetnetwork resources that is equal to the DW_(USER) percentage of totalMainnet staked EOS (“EOS_(ST-TOTAL)”):

% EOS Mainnet Network Resources_((DWuser))=EOS_(ST-USER)/EOS_(ST-TOTAL)

Thus, by way of hypothetical example, if EOS_(ST-TOTAL)=100 EOS, andEOS_(ST-USER)=50 EOS, then DW_(USER) will have exclusive rights to use50% of the EOS Mainnet network resources: This exclusive usage rightexists whether or not DW_(USER) is actually using its 50% of the networkresources it is entitled to. Thus, all other EOS Mainnet users that havestaked the other 50% of EOS_(ST-TOTAL) are limited to 50% of the EOSMainnet network resources even if the other 50% is idle. So, when aDW_(USER) has EOS_(ST-USER) but is not using the network resources thatthe EOS_(ST-USER) entitles DW_(USER) to use then that EOS_(ST-USER)essentially becomes an inefficient allocation of scarce EOS Mainnetnetwork resources.

To address the problem of an inefficient allocation of EOS_(ST-USER) aREX (“Resource EXchange”) system exists for the EOS Mainnet. REX is aleasing market for EOS_(ST-USER). REX allows a voting DW_(USER) with EOSavailable to stake a means to stake an amount of EOS with REX(hereinafter “EOS_(REX-USER)”) and to receive in exchange an equivalentvalue of redeemable but non-transferable and non-tradeable REXcryptographic token. (hereinafter “T-REX”). To be eligible to acquireT-REX a DW_(USER) must first have EOS_(ST-USER) and be voting for atleast twenty-one block producers or be delegating the DW_(USER)EOS_(ST-USER) votes to a proxy. The amount of staked EOS_(REX-USER) willremain in REX until such amount, or more, are received by DW_(USER) fromREX when the T-REX are redeemed by DW_(USER).

By staking the EOS_(REX-USER) with REX instead of just staking with theEOS Mainnet as EOS_(ST-USER) the DW USER makes available to othernetwork users through REX the opportunity to pay EOS leasing fees inexchange for acquiring for a period of time the EOS Mainnet networkresource usage rights associated with EOS_(REX-USER). Thus, over timethe EOS balance in the REX system increases by the amount of leasingfees paid into REX.

At any time after the T-REX maturity period (which is presently fourdays) a DW_(USER) can redeem its acquired T-REX for the then equivalentvalue in EOS. Because the total amount of EOS held by REX will always begreater than or at least equal to the total circulating T-REX there isno risk of loss of value for T-REX, and indeed over time the value ofT-REX will increase. Accordingly, a DW_(USER) redeeming their T-REX mayreceive EOS from REX that is greater in amount than the EOS_(REX-USER)amount originally staked by DW_(USER). The amount of EOS received inexcess of the originally staked EOS_(REX-USER) amount will be passiveincome to DW_(USER).

The preferred exemplary embodiment of the invention deployed on the EOSMainnet uses the REX system to generate passive EOS income for users ofthe lending system. A dApp called DCMICROLOAN comprising one or moresmart contracts, and a loan database, is deployed and executes on theEOS Mainnet to processes loan creations and payments of EOS between EOSMainnet users. For each EOS loan payment made towards the outstandingbalance of an EOS loan created with the system of the present inventiona portion of the EOS loan payment is transferred over as a capitalcontribution to a system investment fund digital wallet (hereinafter“DW_(IF)”). Through execution of a DCMICROLOAN smart contract the EOScapital of DW_(IF) is staked with REX in exchange for T-REX.Periodically through execution of a DCMICROLOAN smart contract thesystem redeems T-REX from REX in exchange for EOS which will hopefullybe greater in amount, but not less than, the amount of EOS originallystaked with REX to acquire the T-REX. The excess amount of EOS will bepassive income for DW_(IF).

For each EOS loan payment made towards the outstanding balance of an EOSloan created with the system a DCMICROLOAN smart contract is executedsuch that both the digital wallet of the loan holder (“DW_(LH)”) anddigital wallet of the payor (“DW_(P)”) will receive a distributionamount of system utility fund tokens (hereinafter “FT”) from a fundtoken digital wallet (“DW_(FT)”) of the system. FT can be transferredbetween EOS Mainnet digital wallets only through execution of aDCMICROLOAN smart contract. Records are created in the loan database ofall FT transfers, from which the digital wallets holding FT and theamount of FT can be determined.

Periodically the at least a portion of the EOS passive income of DW_(IF)is assigned as dividends to the network user digital wallets of recordthat have a balance of FT. The amount of EOS dividend assigned to anetwork user digital wallet is proportional to the digital walletbalance of FT in relation to the total circulating FT. Thus,participants in the EOS Mainnet blockchain loan system of the presentinvention where DC loans are at least partially repaid will receivepassive income, thus creating an incentive system for both lenders andborrowers of the system.

A more detailed description of the preferred exemplary embodiment forthe applicant's P2P blockchain lending system invention is set forthbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic representation of a P2P computer network for usingthe blockchain loan system of the disclosed invention.

FIG. 2 is a schematic representation of a node of the peer-to-peercomputer network of for implementing the blockchain loan systeminvention.

FIG. 3 is a schematic representation of the internal RAM memory a nodeof the peer-to-peer computer network used for the blockchain loan systeminvention.

FIG. 4 is a schematic representation of a blockchain data file of thetype used in the blockchain loan system invention.

FIG. 5 is a schematic representation of a decentralized softwareapplication comprised of “smart contract” code modules for theblockchain loan system invention.

FIG. 6 is a schematic representation of a loan database for a preferredEOS Mainnet embodiment of the blockchain loan system invention.

FIG. 7 is a flow chart of the steps with the blockchain loan systeminvention for recording a new DC loan transaction.

FIG. 8 is a flow chart of the steps with the blockchain loan systeminvention for recording a new DC loan payment transaction.

FIG. 9 is a flow chart of the steps with the blockchain loan systeminvention for assigning fund tokens to the digital wallets of a loanholder and payor.

FIG. 10 is a flow chart of the steps with the blockchain loan systeminvention for investing and redeeming DC EOS with the system investmentfund digital wallet.

FIG. 11 is a flow chart of the steps with the blockchain loan systeminvention for paying a DC dividend with the system investment funddigital wallet to system user digital wallets that have a balance ofsystem fund tokens.

FIG. 12 is a schematic representation of the blockchain loan systeminvention where DW_(LH) is the original lender and DW_(P) is theoriginal borrower.

BEST MODE FOR CARRYING OUT THE INVENTION

The Blockchain Lending System Invention Architecture:

FIG. 1 is a schematic representation of the P2P blockchain network DCloan creation and payment system 10 of the present invention. Referringto FIG. 2 , in the system of the present invention there is a P2Pblockchain computer network 20 that is physically comprised of aplurality of computing system network nodes 30 which can communicatedirectly with each other over an electronic communications network, suchas for example the Internet. Referring to FIG. 3 each network node 30has a computer processor 31, RAM storage memory 32, and a networkcommunications port 33. Each node may also have persistent memorystorage 34, a touch panel input mechanism 35, a keyboard input mechanism36, a radio communications module 37 (e.g. for Wi-Fi networkconnection), and an output display mechanism 38 (e.g. an LCD display).Each node 30 connected to network 20 is a “peer” in the network meaningthat each node 30 can communicate directly with each other node 30 onnetwork 20 without the need for an intermediate central file server. Inother words, each node 30 on network 20 can act as both a file serverand a client on the network.

Referring to FIG. 3 , each peer node 30 on the blockchain P2P network 20has present in node 30 RAM memory 32 for execution by node processor 31a software node daemon 50 which is a protocol for P2P blockchain network20. Node daemon 50 comprises one or more executable computer code filesthat contain operating instructions to facilitate the connection andparticipation by node 30 on the blockchain P2P network 20. Anadministrative node 30 of the system of the present invention may alsocontain in node memory 32 a loan database 60 which stores data relatedto the operation and loans of the system of the present invention. Eachnode 30 of the blockchain P2P blockchain network 20 also contains innode memory 32 a copy of blockchain data file 40.

Referring to FIG. 3 each node 30 of the blockchain P2P blockchainnetwork 20 contains in node memory 32 a copy of a blockchain data file40. FIG. 4 shows blockchain data file 40 as being comprised ofcryptographic data blocks 41. Each block 41 contains a cryptographicallyhashed data set of information and transactions for the blockchain P2Pnetwork 20. Each block 41 after the first block (i.e. “genesis block”)is linked via a pointer back to the block 41 produced before it. Thus, aplurality of blocks 41 are linked together in sequence to form a “chain”of blocks (i.e. a “blockchain”) which will contain all of thetransactions for the blockchain P2P network 20. Each new block 41 isproduced by a block producing node 30. In the exemplary preferred DPoSEOS P2P public blockchain embodiment of the present invention onlyelected block producing nodes 30 are allowed to produce blocks. Eachelected block producing node 30 takes a turn at being the currentlyassigned block producing node 30. Each currently assigned blockproducing node 30 produces blocks for its turn which is a set interval(e.g. presently on the EOS Mainnet a currently assigned block producingturn has an interval of 12 blocks produced which under the current EOSMainnet protocol takes six seconds). Each new block 41 is published onthe blockchain P2P network 20 by the currently assigned block producingnode 30 and is added by each node 30 of the P2P blockchain network 20 toits stored copy of the blockchain data file 40. Thus, all nodes 30 inthe blockchain network will have a copy of the same blockchain data file40.

Every user of a P2P blockchain network 20 must have a digital wallet(“DW”) to enable the user to conduct transactions on P2P blockchainnetwork 20. A DW stores the unique public and private cryptographic keysthat are necessary to interface with P2P blockchain network 20, toconduct transactions, and to check the user balances of DC and othercryptographic tokens (e.g. the FT used in the present invention) on theP2P blockchain network 20. In a preferred embodiment a user of thesystem utilizes a DW to participate in the system.

In a preferred exemplary embodiment of the system of the presentinvention the blockchain P2P network 20 is an EOSIO P2P blockchainnetwork comprised of a plurality of nodes 30 where the node daemon 50includes the core service daemon nodeos. Nodeos is a part of the freeopen-source EOSIO software suite that is produced by the companyBlock.one. The nodeos service daemon 50 runs on every node 30 of theEOSIO P2P blockchain network 20 as it contains the P2P protocol neededfor nodes 30 to communicate with another. The nodeos service daemon alsois configured to process smart contracts, validate transactions, produceblocks containing valid transactions, and add blocks 41 to theblockchain data file 40 of EOSIO P2P blockchain network 20. Each EOSIOP2P blockchain network 20 user of the system of the present inventionwill have a DW capable of interfacing with the EOSIO P2P blockchainnetwork 20 to conduct transactions in DC EOS and the system FT tokens.

The Loans Database Referring to FIG. 6 in the exemplary preferred EOSIOP2P blockchain network 200 there is a loans database 60 for storing dataof the loan creation and payment system. In some embodiments thetransaction data of loans database 60 may be stored as part of the EOSblockchain data file 40 itself. However, for reasons of economy, loansdatabase 60 may be stored off of the blockchain data file 40 in thememory of a system administrator node 30. By way of example and notlimitation loans database 60 may be a Mongodb database that is stored inthe RAM or persistent storage of one or more administrator nodes 30which will be accessed and updated through Demux effects and updaterswhen P2P blockchain network 20 events related to the dApp of the systemare being read or executed. Examples of data storage solutions for loansdatabase 60 may also include, by way of example and not limitation, theuse of the InterPlanetary File System (IPFS) protocol, vRAM, or DISK.

Referring to FIG. 6 loans database 60 comprises a plurality of instancesof data objects (i.e. data structures), each of which is comprised ofindividual record structures having one or more fields for holdingvalues. In the exemplary EOSIO P2P blockchain network 20 each individualdata object may, for example, be declared and instantiated by the EOSIOdApp of the system as a Multi-Index Table. In the illustrated exemplaryembodiment loans database 60 comprises an instance of a loans dataobject 62, fund token data object 64, and DC investment data object 66.

The Loans Data Object 62

Referring to FIG. 6 there is shown a loans data object 62 that containsthe records for all loans created with the system of the presentinvention. There is one record for each loan created. Each record ofloans data object 62 has a structure with field values describing theparticular loan and its terms.

For each loan record there is contemplated to be a loan ID field with aunique identifier for the loan, a timestamp field that stores a datetimevalue for the loan creation, and a DC loan balance field that stores avalue for the amount in DC of the loan balance that remains outstanding.At loan creation the DC loan balance field holds a value for the full DCamount of the loan. As DC loan payments are made towards the loan the DCloan balance field value will be reduced by the amount of the DC loanpayments.

For each loan record there is also contemplated to be a loan holder DWID field that stores the identifier for the DW of the network user thatcurrently holds the loan (hereinafter “DW_(LH)”). In the system of thepresent invention DW_(LH) of a loan record is the DW that is entitled toreceive the proceeds from DC payments made to that DC loan. The DW_(LH)field value of a loan record may be the DW value for the original lenderbut may also be the DW value of different network user who acquired theloan and its rights to repayment by assignment. Any such assignment of aloan between network users would be processed through a call to thesystem dApp which would update the loan holder DW ID field value in theloan data object 62 for the loan record with the new DW_(LH) value.

For each loan record there is also contemplated to be a borrower DW IDfield that stores the identifier for the DW of the network user thatcurrently owes the loan (hereinafter “DW_(B)”). In the system of thepresent invention DW_(B) of a loan record is the DW that is obligated torepay the outstanding balance of the DC loan. The DW_(B) field value ofa loan record may be the DW value for the original borrower but may alsobe the DW value of different network user who assumed the loanobligation by assignment. Any such assignment of a loan obligationbetween network users would be processed through a call to the systemdApp which would update the borrower DW ID field value in the loan dataobject 62 for the loan record with the new DW_(B) value.

For each loan record there is also contemplated to be an agent DW IDfield that stores the identifier for the DW of the network user, if any,that is an agent (hereinafter “DW_(A)”) for the loan. Such an agent maybe an employee of a lender or may be an independent broker for thelender. There may be an arrangement between a lender and agent whereDW_(A) would be entitled to receive DC proceeds from any loan paymentstowards the loan balance in accordance with a commission value stored inan agent commission field of the loan record in loan data object 62.

For each loan record there is also contemplated to be an administratorfee field that stores a value (e.g. a percentage) for the administratorfee to be transferred from DC proceeds on a loan payment to the DW ofthe administrator of the system of the present invention (hereinafter“DW_(SYS)”). There are contemplated to be expenses associated withestablishing, running and maintaining the system of the presentinvention on any P2P blockchain network and the administrator fee isintended to cover and compensate for the network user who incurs suchexpenses.

In the illustrated exemplary embodiment of the invention there is nointerest expense associated with loans created and repaid through thesystem, and no minimum payments or repayment schedule. The economicincentive for both the loan holders and payors of the loan in theillustrated embodiment is the potential DC financial rewards associatedwith participation in the DC investment fund of the system. However, thesystem of the present invention could also be implemented with interestbearing loans, minimum payment requirements, payment schedules and anyother loan terms or conditions. In such embodiments it is contemplatedthat each loan record of loan data object 62 would include fields forstoring values related to these other loan terms and conditions.

The Fund Token Data Object 64

Referring to FIG. 6 there is shown a fund token data object 64 thatcontains records of the FT transactions for each digital wallet that hasreceived FT. Each FT record of the FT data object 64 has a transactionID field that holds a unique value for the record. There is also DW IDfield that stores a value for the DW assignor or assignee of FT for thetransaction. There is an FT amount field that stores the value of FTassigned or received. Upon system deployment a digital wallet for FT(hereinafter “DW_(FT)”) is created by smart contract DCFUNDTOKEN andassigned a genesis balance of FT (hereinafter “FT_(GEN)”). The value forFT_(GEN) of a contemplated preferred embodiment is one billion (1×10⁹)FT, but FT_(GEN) can be set to any value chosen by the systemadministrator.

The DC Investment Data Object 66

Referring to FIG. 6 there is shown a DC investment data object 66 thatcontains a record for each transaction of DC or other cryptographicinvestment token (hereinafter “IT”) of the system investment funddigital wallet DW (hereinafter “DW_(IF)”). Each record of the DCinvestment data object 66 has a transaction ID field that holds a uniquevalue for the record. There is also a timestamp field that stores adatetime value for the DW_(IF) transaction.

There is a category field that stores a value for the category of theDW_(IF) transaction. Contemplated categories include capitalcontribution (a loan payment portion DC addition to DW_(IF)), investment(a payment from DW_(IF) to an investment vehicle such as REX), earnings(an addition to DW_(IF) received from a transaction with an investmentvehicle such as REX), and dividend (a subtraction of DC paid as adividend distribution from DW_(IF) to a DW_(USER) of record in fundtoken data object 64 having an FT balance).

There is a token field that stores a value for the type of cryptographictoken of in the DW_(IF) transaction (e.g. EOS or T-REX). There is atoken amount field that stores a value for the transaction amount oftoken. There is a maturity field which stores a datetime value, asapplicable, for when the token of the transaction (e.g. T-REX) is firsteligible for redemption of sale. There is a redemption status fieldwhich stores a value (i.e. “yes” or “no”), as applicable, indicatingwhether the token of the transaction has been redeemed or sold.

The Blockchain Lending System Software

Referring to FIG. 5 it is shown that dApp DCMICROLOAN 70 for the lendingsystem is comprised of one or more code modules that are executable bynodes 30 of P2P blockchain network 20. In the exemplary illustratedembodiment of the present invention the dApp DCMICROLOAN 70 and is builtfor deployment and execution on EOSIO P2P public blockchain network 20.

DApp DCMICROLOAN 70 of the preferred EOSIO P2P public blockchain networkembodiment is comprised of a plurality of WebAssembly (hereinafter“Wasm”) code files. The Wasm code files that make up the dAppDCMICROLOAN 70 are DCLOAN 71, DCLOANPAY 72, FUNDTOKENS 73, DCINVEST 74,and DCDIVIDEND 75. It should be noted that these code modules are shownby way of example and not limitation, and that fewer or more codemodules, differently named, may also be used. In the preferredembodiment the Wasm code modules are built from source code files thathave preferably been authored in the computer language C++ with theEOSIO Contract Development Toolkit. Each code module that makes up dAppDCMICROLOAN 70 is generally referred to as a “smart contract”.

DCLOAN 71

Referring to FIG. 7 the steps performed by system to create a new DCloan with execution of smart contract DCLOAN are shown. Smart contractDCLOAN is deployed and resides in the blockchain data file 40 stored inthe memory of nodes 30 of the P2P blockchain network 20. Operatinginstructions 80 of DCLOAN will be executed by a node 30 of the P2Pblockchain network 20 to create a new loan.

DCLOAN has one or more operating instructions 81 to receive a request tocreate a new loan on certain terms (e.g. amount, term, interest, etc. .. . ) from a network user lender having a digital wallet DW_(L) to anetwork user borrower having a digital wallet DW_(B). The one or moreoperating instructions 81 in DCLOAN will be executed by a node 30 of theP2P blockchain network 20 to receive a request to create a loan fromDW_(L) to DW_(B) with the communicated terms.

DCLOAN has one or more operating instructions 82 to confirm that DW_(L)has a sufficient balance of DC to cover the new loan, or else return amessage to DW_(L) and DW_(B) declining the transaction to create a newloan. The one or more operating instructions 82 in DCLOAN will beexecuted by a node 30 of the P2P blockchain network 20 to confirm thatDW_(L) has a sufficient balance of DC to cover the new loan, or elsereturn a message to DW_(L) and DW_(B) declining the transaction tocreate a new loan.

DCLOAN has one or more operating instructions 83 to communicate the loanterms to DW_(B) and confirm acceptance by DW_(B) of the loan terms, orelse return a message to DW_(L) and DW_(B) declining the transaction tocreate a new loan. The one or more operating instructions 82 in DCLOANwill be executed by a node 30 of the P2P blockchain network 20 toconfirm acceptance by DW_(B) of the loan terms, or else return a messageto DW_(L) and DW_(B) declining the transaction to create a new loan.

DCLOAN also contains one or more operating instructions 84 for creatingand populating the fields of a new loan record in loan data object 62with the new loan information. The one or more operating instructions 84will be executed by a node 30 of the P2P blockchain network 20 to createa new loan record in loan data object 62 and populate the record fieldswith the new loan information. The transaction updating the state ofloan data object 62 (i.e. updated data set with the new loan record)that results from execution of operating instructions 84 will beincluded in the next cryptographic block 41 that produced forpublication and addition to the blockchain 40.

DCLOAN also contains one or more operating instructions 85 for recordingthe loan transaction on blockchain 40 including the transfer of a loanamount of DC from the DC balance of DW_(L) to the DC balance of DW_(B).The one or more operating instructions 85 will be executed by a node 30of the P2P blockchain network 20 to record the loan transaction onblockchain 40 including the transfer of a loan amount of DC from the DCbalance of DW_(L) to the DC balance of DW_(B).

DCLOANPAY 72

FIG. 8 shows the steps 90 performed by the system for processing a loanpayment from a network user payor WEB3 digital wallet (hereinafter“DW_(P)”) to a network user WEB3 digital wallet of the record loanholder (hereinafter “DW_(LH)”) to reduce the outstanding loan balancefield value for a loan record in loans data object 62. DCLOANPAY isdeployed and resides in the blockchain data file 40 stored in the memoryof nodes 30 of the P2P blockchain network 20.

DCLOANPAY contains one or more operating instructions 91 for receiving aloan payment request from DW_(P). The received loan payment request mustcommunicate data to DCLOANPAY which includes a loan ID and a DC paymentamount. The one or more operating instructions 91 will be executed by anode 30 of the P2P blockchain network 20 to receive from DW_(P) a loanpayment request that communicates data to DCLOANPAY which includes aloan ID and a DC payment amount.

DCLOANPAY also contains one or more operating instructions 92 forconfirming the existence in loans data object 62 of a record with a loanID field value matching the loan ID communicated by DW_(P) and which hasa loan balance field value greater than zero but less than or equal tothe DC payment amount communicated by DW_(P), or else return an errormessage to DW_(P) declining the transaction. The one or more operatinginstructions 92 will be executed by the a node 30 of the P2P blockchainnetwork 20 to confirm the existence in loans data object 62 of a recordwith a loan ID field value matching the loan ID communicated by DW_(P)and which has a loan balance field value greater than zero but less thanor equal to the DC payment amount communicated by DW_(P), or else returnan error message to DW_(P) declining the transaction.

DCLOANPAY also contains one or more operating instructions 93 forconfirming that DW_(P) has a sufficient balance of DC to cover the DCloan payment amount, or else return an error message declining thetransaction. The one or more operating instructions 93 will be executedby a node 30 of the P2P blockchain network 20 to confirm that DW_(P) hasa sufficient balance of DC to cover the DC loan payment amount, or elsereturn an error message declining the transaction.

DCLOANPAY also contains one or more operating instructions 94 fordetermining a payment division of the DC loan payment amount from DW_(P)between DW_(SYS), DW₁, and DW_(LH) and DW_(A) (if any) identified in theconfirmed loan record. The one or more operating instructions 94 will beexecuted by a node 30 of the P2P blockchain network 20 to determine apayment division of the DC loan payment amount between DW_(SYS), DW₁,and DW_(LH) and DW_(A) (if any) identified in the confirmed loan record.In a preferred exemplary embodiment, the payment division comprisesindividual loan payment portions (hereinafter “LPP”):

-   -   LPP_(DWsys)=0.5%*DC Loan Payment Amount    -   LPP_(DWi)=0.5%*DC Loan Payment Amount    -   LPP_(DWa)=Commission Field Value*DC Loan Payment Amount    -   LPP_(DWlh)=DC Loan Payment        Amount−LPP_(DWsys)−LPP_(DWi)−LPP_(DWa)    -   LPP_(DWsys)+LPP_(DWi)+LPP_(DWa)+LPP_(DWlh)=DC Loan Payment        Amount

Thus, the payment division determined for the DC loan payment amount iscomprised of (1) LPP_(DWsys) which is the determined loan paymentportion of the DC loan payment amount that will be transferred fromDW_(P) to DW_(SYS); (2) LPP_(DWi) which is the determined loan paymentportion of the DC loan payment amount that will be transferred fromDW_(P) to DW_(I); (3) LPP_(DWa) which is the determined loan paymentportion of the DC loan payment amount that will be transferred fromDW_(P) to the DW_(A) value of the agent ID field for the confirmed loanrecord and is calculated from the commission field value of theconfirmed loan record; and LPP_(DWlh) is the determined loan paymentportion of the DC loan payment amount that will be transferred fromDW_(P) to the DW_(LH) value of the loan holder ID field for the loanrecord.

DCLOANPAY also contains one or more operating instructions 95 forreducing the value of the loan balance field for the confirmed loanrecord in loan data object 62 by the DC loan payment amount from DW_(P).The one or more operating instructions 95 will be executed by a node 30of the P2P blockchain network 20 to reduce the value of the loan balancefield for the confirmed loan record in loan data object 62 by the DCloan payment amount from DW_(P). The updated state (i.e. a data set withnew loan balance field value for the confirmed loan record) of loan dataobject 62 resulting from execution of operating instructions 95 will beincluded by a block producing node 30 in the next cryptographic block 41that the node produces for publication and addition to the blockchain40.

DCLOANPAY also contains one or more operating instructions 96 forcommunicating to smart contract FUNDTOKENS, with each successfullyprocessed DC loan payment request, a request to distribute system FT.The communicated request must contain data that includes the DC paymentamount, DW_(P) and DW_(LH). The one or more operating instructions 96will be executed by a node 30 of the P2P blockchain network 20 tocommunicate to smart contract FUNDTOKENS a request to distribute FT. Thecommunicated request contains data the includes the DC payment amount,DW_(P) and DW_(LH).

DCLOANPAY also contains one or more operating instructions 97 forrecording a transaction of the divisional transfer from DW_(P) of the DCloan payment amount on blockchain 40 for (1) the transfer from DW_(P) ofthe determined LPP_(DWsys) to DW_(SYS); (2) the transfer from DW_(P) ofthe determined LPP_(DWi) to DW_(I); (3) the transfer from DW_(P) of thedetermined LPP_(DWa) to DW_(A); and (4) the transfer from DW_(P) of thedetermined LPP_(DWlh) to the DW_(LH). The one or more operatinginstructions 97 will be executed by a node 30 of the P2P blockchainnetwork 20 to record a transaction of the divisional transfer fromDW_(P) of the DC loan payment amount on blockchain 40 for (1) thetransfer from DW_(P) of the determined LPP_(DWsys) to DW_(SYS); (2) thetransfer from DW_(P) of the determined LPP_(DWi) to DW_(I); (3) thetransfer from DW_(P) of the determined LPP_(DWa) to DW_(A); and (4) thetransfer from DW_(P) of the determined LPP_(DWlh) to the DW_(LH). Theupdated states DW_(P), DW_(LH), DW_(SYS), DW₁, and DW_(A) (if any)resulting from execution of operating instructions 97 will be includedby a block producing node 30 in the next cryptographic block 41 that thenode produces for publication and addition to the blockchain 40.

DCFUNDTOKENS 73

FIG. 9 shows the steps 100 performed by the system smart contractDCFUNDTOKENS for distributing fund tokens to DW_(LH) and DW_(P) for aloan when a DC loan payment is made by DW_(P). Smart contractDCFUNDTOKENS is deployed and resides in the blockchain data file 40stored in the memory of nodes 30 of the P2P blockchain network 20.

Smart contract FUNDTOKENS contains one or more operating instructions110 for receiving a communication from smart contract DCLOANPAY 72 datafor the DC payment amount, DW_(P) and DW_(LH). The one or more operatinginstructions 110 will be executed by a node 30 of the P2P blockchainnetwork 20 to receive a communication from smart contract DCLOANPAY 72of data for the DC payment amount, DW_(P) and DW_(LH).

FUNDTOKENS also contains one or more operating instructions 120 fordetermining an FT transfer amount (hereinafter “FT_(TA)”) from the inputof the DC payment amount and the field value of the FT_(CONV) in thefund token data object 64. In a preferred embodiment the one or moreoperating instructions 120 will be executed by a node 30 of the P2Pblockchain network 20 to determine FT_(TA) as being equal to the productof the DC loan payment amount multiplied by the current field value ofFT_(CONV) in the fund token data object 64:

FT_(TA)=DC loan payment amount*FT_(CONV)

Smart contract FUNDTOKENS of the preferred exemplary embodiment alsocontains one or more operating instructions 130 for recording atransaction of the transfer of FT_(TA) from DW_(FT) to DW_(P) onblockchain 40. The one or more operating instructions 130 will beexecuted by a node 30 of the P2P blockchain network 20 to record atransaction of the transfer of FT_(TA) from DW_(FT) to DW_(P) onblockchain 40. The updated states DW_(P) and DW_(FT) resulting fromexecution of operating instructions 130 will be included by a blockproducing node 30 in the next cryptographic block 41 that the nodeproduces for publication and addition to the blockchain 40.

The FT balance for a network wallet DW_(USER) on the P2P blockchainnetwork 20 is used to calculate the periodic dividend distribution fromDW_(IF) to DW_(USER). In a preferred embodiment a record of eachDW_(USER) FT transaction is kept by the system, and FT can only beassigned to a DW_(USER), whether from DW_(FT) or another DW_(USER),through the smart contract FUNDTOKENS.

Therefore, for each FT transaction that happens there is a recordcreated by FUNDTOKENS in fund token data object 64. Each such record hasa DW_(USER) ID field that stores a value identifying the DW_(USER) (e.g.the public key of DW_(USER)) and an FT amount field that stores thevalue for the amount of FT in the transaction.

Smart contract FUNDTOKENS therefore also contains one or more operatinginstructions 140 for creating in fund token data object 64 a record ofthe FT transaction with a DW ID field that stores the identifying valueof DW_(P), and the FT amount field storing the value FT_(TA).

Smart contract FUNDTOKENS of the preferred exemplary embodiment alsocontains one or more operating instructions 150 for recording atransaction of the transfer of FT_(TA) from DW_(FT) to DW_(LH) onblockchain 40. The one or more operating instructions 150 will beexecuted by a node 30 of the P2P blockchain network 20 to record atransaction of the transfer of FT_(TA) from DW_(FT) to DW_(LH) onblockchain 40. The updated states DW_(LH) and DW_(FT) resulting fromexecution of operating instructions 150 will be included by a blockproducing node 30 in the next cryptographic block 41 that the nodeproduces for publication and addition to the blockchain 40.

Smart contract FUNDTOKENS of the preferred exemplary embodiment alsocontains one or more operating instructions 160 for creating in fundtoken data object 64 a record of an FT transaction with a DW ID fieldthat stores the identifying value of DW_(LH), and the FT amount fieldstoring the value FT_(TA).

Smart contract FUNDTOKENS of the preferred exemplary embodiment alsocontains one or more operating instructions 170 for a block producingnode 30 to update the state of fund token data object 64 resulting fromexecution of operating instructions 140 and 160 in the nextcryptographic block 41 that the node produces for publication andaddition to the blockchain 40.

DCINVEST 74

FIG. 10 shows the steps 200 performed by the smart contract DCINVEST 74for the investment and earnings of EOS from DW_(IF) when the inventionis deployed onto EOS Mainnet 20. Smart contract DCINVEST is deployed andresides in the blockchain 40 stored in the memory of nodes 30 of EOSMainnet 20.

Smart contract DCINVEST contains one or more operating instructions 205for initializing an investment event listener for either a request foran EOS transfer from DW_(IF) to REX to acquire T-REX tokens, or aredemption period elapse. The one or more operating instructions 205will be executed by a node 30 of the EOS Mainnet 20 to initialize aninvestment event listener for either a request for an EOS transfer fromDW_(IF) to REX to acquire T-REX tokens, or a redemption period elapse.

Smart contract DCINVEST contains one or more operating instructions 210for confirming a request for an EOS transfer from DW_(IF) to REX toacquire T-REX tokens, or else confirming a redemption period elapse. Theone or more operating instructions 210 will be executed by a node 30 ofthe EOS Mainnet 20 to confirm a request for an EOS transfer from DW_(IF)to REX to acquire T-REX tokens, or else confirm a redemption periodelapse.

Smart contract DCINVEST contains one or more operating instructions 215for recording a transaction of the transfer of EOS from DW_(IF) to REXon blockchain 40. The one or more operating instructions 215 will beexecuted by a node 30 of the EOS Mainnet 20 to record a transaction ofthe transfer of EOS from DW_(IF) to REX on blockchain 40.

Smart contract DCINVEST contains one or more operating instructions 220for recording a transaction of the transfer of T-REX from REX to DW_(IF)on blockchain 40. The one or more operating instructions 220 will beexecuted by a node 30 of the EOS Mainnet 20 to record a transaction ofthe transfer of T-REX from REX to DW_(IF) on blockchain 40.

Smart contract DCINVEST contains one or more operating instructions 225for creating a record in investment data object 66 of the transfer ofT-REX from REX to DW_(IF), including setting the field values foramount, maturity, and redemption status. The one or more operatinginstructions 225 will be executed by a node 30 of the EOS Mainnet 20 tocreate a record in investment data object 66 of the transfer of T-REXfrom REX to DW_(IF), including but not limited to setting the fieldvalues for amount, maturity, and redemption status.

Smart contract DCINVEST contains one or more operating instructions 230for updating the state for the investment data object 66 (i.e. the newT-REX transaction record) on blockchain 40 and reinitializing theinvestment event listener. The one or more operating instructions 230will be executed by a node 30 of the EOS Mainnet 20 to update the statefor the investment data object 66 (i.e. the new T-REX transactionrecord) on blockchain 40 and reinitialize the investment event listener.

Smart contract DCINVEST contains one or more operating instructions 235for confirming a redemption period elapse, or else reinitializing theinvestment event listener. The one or more operating instructions 235will be executed by a node 30 of the EOS Mainnet 20 to confirm aredemption period elapse, or else reinitialize the investment eventlistener.

Smart contract DCINVEST contains one or more operating instructions 240for confirming that investment data object 66 has one or more records ofa transaction for T-REX that has a maturity field datetime value thathas passed, and also has a redemption status field value of empty or“no” (hereinafter any such Mature and UnRedeemed T-REX record beingreferred to as “T-REX_(MUR)”), or else reinitializing the investmentevent listener. The one or more operating instructions 240 will beexecuted by a node 30 of the EOS Mainnet 20 to confirm that investmentdata object 66 has one or more T-REX_(MUR) records, or else reinitializethe investment event listener.

Smart contract DCINVEST also contains one or more operating instructions245 for determining the total amount of mature and unredeemed T-REX(hereinafter “T-REX_(MUR-TOTAL)”) as being equal to the sum of the tokenamount field values for the T-REX_(MUR) records that were identifiedfrom execution of the one or more operating instructions 240. The one ormore operating instructions 230 will be executed by a node 30 of EOSMainnet 20 to determine a T-REX_(MUR-TOTAL) as being equal to the sum ofthe token amount field values for the T-REX_(MUR) records that wereidentified from execution of the one or more operating instructions 240.

Smart contract DCINVEST also contains one or more operating instructions245 for recording on blockchain 40 a redemption assignment from DW_(IF)to REX of T-REX tokens in an amount equal to T-REX_(MUR-TOTAL) inexchange for receiving from REX an amount EOS_(REX-RDM) of EOS. The oneor more operating instructions 245 will be executed by a node 30 of theEOS Mainnet 20 to record on blockchain 40 a redemption assignment ofT-REX from DW_(IF) to REX in an amount T-REX_(MUR-TOTAL) and assignmentto DW_(IF) from REX an amount EOS_(REX-RDM) of EOS.

Smart contract DCINVEST also contains one or more operating instructions250 for, upon a redemption assignment from DW_(IF) to REX ofT-REX_(MUR-TOTAL), adjusting the redemption status field value to “yes”for each of the T-REX_(MUR) records in investment data object 66 thatwere identified from execution of the one or more operating instructions240. The one or more operating instructions 250 will be executed by anode 30 of the EOS Mainnet 20 to, upon a redemption assignment fromDW_(IF) to REX of T-REX_(MUR-TOTAL), adjust the redemption status fieldvalue to “yes” for each of the T-REX_(MUR) records in investment dataobject 66 that were identified from execution of the one or moreoperating instructions 240. The updated state of investment data object66 resulting from execution of operating instructions 250 will beincluded by a block producing node 30 in the next cryptographic block 41that the node produces for publication and addition to the blockchain40.

Smart contract DCINVEST contains one or more operating instructions 260for, after a redemption assignment from DW_(IF) to REX ofT-REX_(MUR-TOTAL), resetting the redemption period and reinitializingthe investment event listener of the one or more operating instruction205. The one or more operating instructions 260 will be executed by anode 30 of EOS Mainnet 20 after a redemption assignment from DW_(IF) toREX of T-REX_(MUR-TOTAL) to reset the redemption period and reinitializethe investment event listener of the one or more operating instruction205.

DCDIVIDEND 75

FIG. 11 shows the steps 300 performed by the smart contract DCDIVIDENDfor assigning a dividend amount of DC (hereinafter “DC_(DIV)”) to thenetwork user digital wallets of record in fund token data object 64 thathave a balance of FT. DC_(DIV) is an amount of DC that is set by thesystem to be calculated as being equal to a predetermined portion of theDC passive income for DW_(IF). In a preferred embodiment DC_(DIV) iscalculated as being equal to 50% of the DC passive income for DW_(IF).However, any percentage of DC passive income for DW_(IF) may be used. Inthe preferred embodiment smart contract DCDIVIDEND is deployed andresides in the blockchain 40 stored in the memory of nodes 30 of EOSMainnet 20.

Smart contract DCDIVIDEND contains one or more operating instructions310 for determining at a predetermined time the DC_(DIV) to pay out tothe network user digital wallets of record in fund token data object 64that have a balance of FT. The predetermined dividend time in apreferred EOS Mainnet embodiment is every twenty-four hours, howeverthis may be set to any time interval. The one or more operatinginstructions 310 will be executed by a node 30 of the EOS Mainnet 20 ata predetermined dividend time to determine the DC_(DIV) to pay out tothe network user digital wallets of record in fund token data object 64that have a balance of FT.

Smart contract DCDIVIDEND also contains one or more operatinginstructions 320 for identifying at the predetermined time from fundtoken data object 64 each digital wallet having an FT balance fieldvalue greater than zero (hereinafter “DW_(USER-FT)”), and summing the FTbalances for all DW_(USER-FT) records to determine a value for thecirculating FT circulation value (hereinafter “FT_(CIRC)”). The one ormore operating instructions 320 will be executed by a node 30 of the EOSMainnet 20 at the predetermined time to identify from fund token dataobject 64 each digital wallet having an FT balance field value greaterthan zero (hereinafter “DW_(USER-FT)”), and summing the FT balances forall DW_(USER-FT) records to determine a value for the circulating FTcirculation value (hereinafter “FT_(CIRC)”).

Smart contract DCDIVIDEND also contains one or more operatinginstructions 330 to calculate at the predetermined time for eachDW_(USER-FT) a DC dividend distribution (hereinafter “DW_(USER-DCDIV)”)that is equal to the product of the dividend amount multiplied times theFT percentage that DW_(USER-FT) has of FT_(CIRC). Thus, for example, ifdividend amount=one hundred (100) EOS, FTcmRc=one thousand (1000), andDW_(USER-FT) has an FT balance field value of one hundred (100), thenDW_(USER-DIV) would be equal to ten (10) EOS:

DW_(USER-DCDIV)=[DW_(USER-FTBAL)/FT_(CIRC)]*Dividend Amount

DW_(USER-DCDIV)=[100/1000]*100 EOS

DW_(USER-DCDIV)[0.1]*100 EOS

DW_(USER-DCDIV)=10 EOS

The one or more operating instructions 330 will be executed by a node 30of the EOS Mainnet 20 at the predetermined time to calculate for eachDW_(USER-FT) a DC dividend distribution (hereinafter “DW_(USER-DCDIV)”)that is equal to the product of the dividend amount multiplied times theFT percentage that DW_(USER-FT) has of FT_(CIRC).

Smart contract DCINVEST also contains one or more operating instructions340 for recording on blockchain 40 for each determined DW_(USER-DCDIV)an assignment from DW_(IF) of the DW_(USER-DCDIV) amount of EOS toDW_(USER). The one or more operating instructions 340 will be executedby a node 30 of the EOS Mainnet 20 to record on blockchain 40 for eachdetermined DW_(USER-DCDIV) an assignment from DW_(IF) of theDW_(USER-DCDIV) amount of EOS to DW_(USER).

While particular embodiments and applications of the present blockchaincryptocurrency loan system invention have been shown and describedchanges and modifications may be made, and the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the invention.

1. A computer-implemented method for transacting among a plurality ofnodes in a blockchain network, the blockchain network implementing aproof-of-stake protocol for controlling block production in theblockchain network, comprising: creating, on the blockchain network, asmart contract configured to loan an amount of first tokens from a firstdigital wallet associated with a first node of the blockchain network toa second digital wallet associated with a second node of the blockchainnetwork; in response to repayment of part of the amount of the firsttoken by a payer digital wallet to a loan holder digital wallet,automatically allocating a first portion of the repayment to a systemdigital wallet, a second portion of the repayment to an investmentdigital wallet, and a third portion of the repayment to the loan holderdigital wallet; and in response to the repayment, automaticallyallocating a first amount of a fund token to the payer digital walletand a second amount of the fund token the loan holder digital wallet. 2.The computer-implemented method of claim 1, wherein the first digitalwallet comprises the payer digital wallet, and wherein the seconddigital wallet comprises the loan holder digital wallet.
 3. Thecomputer-implemented method of claim 1, further comprising:automatically allocating a dividend amount of the first token to eachdigital wallet in the blockchain network comprising a balance of fundtokens.
 4. The computer-implemented method of claim 3, furthercomprising: staking at least a portion of the first tokens allocated tothe investment digital wallet, wherein the dividend amount is generatedfrom staking the at least a portion of the first tokens.
 5. Thecomputer-implemented method of claim 1, further comprising: updating abalance of the amount of the first token loaned; and including theupdated balance in a next cryptographic block produced by a blockproducing node of the blockchain network.
 6. The computer-implementedmethod of claim 1, wherein the first amount and the second amount of thefund token are automatically allocated based on a second smart contracton the blockchain network.
 7. A system for transacting among a pluralityof nodes in a blockchain network, the blockchain network implementing aproof-of-stake protocol for controlling block production in theblockchain network, comprising at least one processor configured as anode in the blockchain network and configured to: create, on theblockchain network, a smart contract configured to loan an amount of afirst token from a first digital wallet associated with a first node ofthe blockchain network to a second digital wallet associated with asecond node of the blockchain network; in response to repayment of partof the amount of the first token by a payer digital wallet to a loanholder digital wallet, automatically allocate a first portion of therepayment to a system digital wallet, a second portion of the repaymentto an investment digital wallet, and a third portion of the repayment tothe loan holder digital wallet; and in response to the repayment,automatically allocate a first amount of a fund token to the payerdigital wallet and a second amount of the fund token the loan holderdigital wallet.
 8. The system of claim 7, wherein the first digitalwallet comprises the payer digital wallet, and wherein the seconddigital wallet comprises the loan holder digital wallet.
 9. The systemof claim 8, wherein the at least one processor is further configured to:automatically allocate a dividend amount of the first token to eachdigital wallet in the blockchain network comprising a balance of fundtokens.
 10. The system of claim 9, wherein the at least one processor isfurther configured to: stake at least a portion of the first tokensallocated to the investment digital wallet, wherein the dividend amountis generated from staking the at least a portion of the first tokens.11. The system of claim 8, wherein the at least one processor is furtherconfigured to: update a balance of the amount of the first token loaned;and include the updated balance in a next cryptographic block producedby a block producing node of the blockchain network.
 12. The system ofclaim 8, wherein the first amount and the second amount of the fundtoken are automatically allocated based on a second smart contract onthe blockchain network.
 13. A computer program product for transactingamong a plurality of nodes in a blockchain network, the blockchainnetwork implementing a proof-of-stake protocol for controlling blockproduction in the blockchain network, comprising at least onenon-transitory computer-readable medium including instructions that,when executed by at least one processor of a node in the blockchainnetwork, cause the processor to: create, on the blockchain network, asmart contract configured to loan an amount of a first token from afirst digital wallet associated with a first node of the blockchainnetwork to a second digital wallet associated with a second node of theblockchain network; in response to repayment of part of the amount ofthe first token by a payer digital wallet to a loan holder digitalwallet, automatically allocate a first portion of the repayment to asystem digital wallet, a second portion of the repayment to aninvestment digital wallet, and a third portion of the repayment to theloan holder digital wallet; and in response to the repayment,automatically allocate a first amount of a fund token to the payerdigital wallet and a second amount of the fund token the loan holderdigital wallet.
 14. The computer program product of claim 13, whereinthe first digital wallet comprises the payer digital wallet, and whereinthe second digital wallet comprises the loan holder digital wallet. 15.The computer program product of claim 14, wherein the at least oneprocessor is further caused to: automatically allocate a dividend amountof the first token to each digital wallet in the blockchain networkcomprising a balance of fund tokens.
 16. The computer program product ofclaim 15, wherein the at least one processor is further caused to: stakeat least a portion of the first tokens allocated to the investmentdigital wallet, wherein the dividend amount is generated from stakingthe at least a portion of the first tokens.
 17. The computer programproduct of claim 13, wherein the at least one processor is furthercaused to: update a balance of the amount of the first token loaned; andinclude the updated balance in a next cryptographic block produced by ablock producing node of the blockchain network.
 18. The computer programproduct of claim 13, wherein the first amount and the second amount ofthe fund token are automatically allocated based on a second smartcontract on the blockchain network.